This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
There is not technically one kit that upgrades from 7.0.x to 8.0.x FPx or 8.5.x FPx, but what you can do is use the chaining of Smart Upgrade kits to accomplish this. What you will have is:
1 Kit going from 7 to 8, example:
Release 7.0.3 ---> Release 8.5.1
Then 1 kit going from 8.5.1 to 8.5.1 FP3
Release 8.5.1 ---> Release 8.5.1 FP3
*NOTE* In this situation, BOTH kits will need to have "basic" set for the "source configuration". This is because the 7.0.x client is considered "basic", and although you will be going from 7.0.x (basic) to 8.5.1 (standard) to 8.5.1 FP3 (standard), the 7.0.x client sees the upgrade path all at once based on its current configuration.
Once these kits are configured correctly, if the client is either prompted or manually selects Tools - Smart Upgrade from the File menu, the prompt will show that the upgrade can go to 8.5.1 FP3. The client will then download 8.5.1 and 8.5.1 FP3, shut down, install them in order, and, if you have specified, restart after the upgrade has completed.
One known issue with prompting in this situation: When admins usually set this up, they pair it with a Desktop Settings document which lists Release 8.5.1 FP3 as the deploy version. In situations where you are "chaining" the smart upgrades, the user will not be automatically prompted to upgrade, but must go to Tools - Smart upgrade manually. This issue is fixed in 8.5.2, and a workaround is to leave the Deploy Version field blank in the desktop policy document.
If this is attempted and seems to be working contrary to design, please open a ticket with support for investigation.
Feedback response number WEBB87DLRK created by ~Julia Zekgeromanjip on 07/15/2010